Checkpointing For Delayed Alert Creation

ABSTRACT

Methods, apparatuses, and computer program products for checkpointing for delayed alert creation are provided. Embodiments include applying a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered and following a crash and loss of the corresponding alerts not recorded in an alert database, generating new alerts based on the events in the events pool having the checkpoint. In response to completing processing of a new alert, embodiments include determining whether the alert database has an entry corresponding to the processed new alert. If the alert database has an entry corresponding to the processed new alert, embodiments include delivering the processed new alert without reporting the processed new alert to the alert database. If the alert database does not have an entry corresponding to the processed new alert, embodiments include reporting the processed new alert to an alert database.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically, methods, apparatuses, and computer program products for checkpointing for delayed alert creation in a distributed processing system.

2. Description of Related Art

The development of the EDVAC computer system of 1948 is often cited as the beginning of the computer era. Since that time, computer systems have evolved into extremely complicated devices. Today's computers are much more sophisticated than early systems such as the EDVAC. Computer systems typically include a combination of hardware and software components, application programs, operating systems, processors, buses, memory, input/output devices, and so on. As advances in semiconductor processing and computer architecture push the performance of the computer higher and higher, more sophisticated computer software has evolved to take advantage of the higher performance of the hardware, resulting in computer systems today that are much more powerful than just a few years ago.

Modern distributed processing systems for intensive computing may have millions of devices with many processes running on each device all of which are capable of error and status reporting for automated error recovery, reporting to a systems administrator, and for other reasons. In many cases, in the case of an error for example, the sheer number of such error reports and status reports are so overwhelming that they cannot be handled in a meaningful manner. For example, a systems administrator receiving a hundred thousand error reports may be overwhelmed by the sheer number of such reports and therefore in the aggregate those reports become more and more unhelpful and irrelevant.

SUMMARY OF THE INVENTION

Methods, apparatuses, and computer program products for checkpointing for delayed alert creation are provided. Embodiments include an event and alert analysis module applying a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered. Following a crash and the loss of the corresponding alerts not recorded in an alert database, the event and alert analysis module generates new alerts based on the events in the events pool having the checkpoint. In response to completing processing of a new alert, the event and alert analysis module determines whether the alert database has an entry corresponding to the processed new alert. If the alert database has an entry corresponding to the processed new alert, the event and alert analysis module delivers the processed new alert without reporting the processed new alert to the alert database. If the alert database does not have an entry corresponding to the processed new alert, the event and alert analysis module writes the processed new alert to a delivery queue and reports the processed new alert to the alert database including creating an entry within the alert database.

The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary system for checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

FIG. 2 sets forth a block diagram of automated computing machinery comprising an exemplary computer useful in checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

FIG. 3 sets forth a block diagram of an exemplary system for checkpointing for delayed alert creation in a distributed processing system in a distributed processing system according to embodiments of the present invention.

FIG. 4 sets forth a diagram illustrating assigning events to an events pool according to embodiments of the present invention.

FIG. 5 sets forth a diagram illustrating assigning alerts to an alerts pool according to embodiments of the present invention.

FIG. 6 sets forth a flow chart illustrating an example method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

FIG. 7 sets forth a flow chart illustrating an additional method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

FIG. 8 sets forth a flow chart illustrating an additional method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

FIG. 9 sets forth a flow chart illustrating an additional method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary methods, apparatuses, and computer program products for checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention are described with reference to the accompanying drawings, beginning with FIG. 1. FIG. 1 illustrates an exemplary system for checkpointing for delayed alert creation in a distributed processing system (101) according to embodiments of the present invention. A distributed processing system is typically implemented as multiple autonomous or semi-autonomous computers that communicate through a computer network. In such example distributed processing systems, the computers often interact with each other in order to achieve a common goal. A computer program that runs in such an example distributed system is typically called a distributed program, and distributed programming is often used to describe the process of writing such programs.

In the example of FIG. 1, the distributed processing system (101) is implemented as a parallel computer (100), non-volatile memory for the computer in the form of data storage device (118), an output device for the computer in the form of a printer (120), and an input/output device for the computer in the form of a computer terminal (122). The parallel computer (100) in the example of FIG. 1 includes a plurality of compute nodes (102). Each compute node is an automated computing device composed of one or more computer processors, its own computer memory, and its own input/output functionality. The compute nodes (102) are coupled for data communications by several independent data communications networks including a high speed Ethernet network (174), a Joint Test Action Group (‘JTAG’) network (104), a collective or tree network (106) which is optimized for collective operations, and a torus network (108) which is optimized for point to point operations. The tree network (106) is a data communications network that includes data communications links connected to the compute nodes so as to organize the compute nodes as a tree. Each data communications network is implemented with data communications links among the compute nodes (102). The data communications links provide data communications for parallel operations among the compute nodes of the parallel computer (100).

In addition to the compute nodes (102), the parallel computer (100) includes input/output (‘I/O’) nodes (110, 114) coupled to the compute nodes (102) through the high speed Ethernet network (174). The I/O nodes (110, 114) provide I/O services between the compute nodes (102) and I/O devices, which in this example is the data storage device (118), the printer (120) and the terminal (122). The I/O nodes (110, 114) are connected for data communications through a local area network (‘LAN’) (130). The parallel computer (100) also includes a service node (116) coupled to the compute nodes (102) through the JTAG network (104). The service node (116) provides service common to the compute nodes (102), such as loading programs into the compute nodes (102), starting program execution on the compute nodes (102), retrieving results of program operations on the compute nodes (102), and so on. The service node (116) runs an event and alert analysis module (124) and communicates with a system administrator (128) through a service application interface (126) that runs on the computer terminal (122).

Many of the components of the distributed processing system of FIG. 1, that is the devices of the distributed processing system or processes running on the devices of the distributed processing system of FIG. 1, are capable of some form of error or status reporting through events and many of such components are also capable of receiving alerts in response to one or more of such events. Often in distributed processing systems hundreds of thousands or millions of components may provide or receive incidents, often in the form of events or alerts.

An incident is a generic term used in this specification to mean an identification or notification of a particular occurrence on a component of a distributed processing system such as events described below, a refined identification of an occurrence often based on events such as an alert described below, or other notifications as will occur to those of skill in the art.

Incidents are administered in pools for event and alert analysis according to embodiments of the present invention. A pool of incidents is a collection of incidents organized by the time of either their occurrence, by the time they are logged in an incident queue, included in the pool, or other time as will occur to those of skill in the art. Such incident pools often provide the ability to analyze a group of time related incidents. Often such incident pools are useful in identifying fewer and more relevant incidents in dependence upon multiple related incidents.

An event according to embodiments of the present invention is a notification of a particular occurrence in or on a component of the distributed processing system. Such events are sent from the component upon which the occurrence occurred or another reporting component to an event and alert analysis module according to the present invention. Often events are notifications of errors occurring in a component of the data processing system. Events are often implemented as messages either sent through a data communications network or shared memory. Typical events for event and alert analysis according to embodiments of the present invention include attributes such as an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component, and other attributes.

An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error, based upon more than one event and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

The event and alert analysis module (124) includes at least two incident analyzers implemented as an event analyzer and an alert analyzer capable of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. The event and alert analysis module (124) is also implemented as a monitor and checkpoint manager for managing the checkpoints from the incident analyzers.

Specifically, the event and alert analysis module (124) is implemented as automated computing machinery configured to apply a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered. Following a crash and the loss of the corresponding alerts not recorded in an alert database, the event and alert analysis module (124) is configured to generate new alerts based on the events in the events pool having the checkpoint. In response to completing processing of a new alert, the event and alert analysis module (124) determines whether the alert database has an entry corresponding to the processed new alert. If the alert database has an entry corresponding to the processed new alert, the event and alert analysis module (124) delivers the processed new alert without reporting the processed new alert to the alert database. If the alert database does not have an entry corresponding to the processed new alert, the event and alert analysis module (124) writes the processed new alert to a delivery queue and reports the processed new alert to the alert database including creating an entry within the alert database.

The arrangement of nodes, networks, and I/O devices making up the exemplary distributed processing system illustrated in FIG. 1 are for explanation only, not for limitation of the present invention. Distributed data processing systems configured to perform checkpointing for delayed alert creation according to embodiments of the present invention may include additional nodes, networks, devices, and architectures, not shown in FIG. 1, as will occur to those of skill in the art. The parallel computer (100) in the example of FIG. 1 includes sixteen compute nodes (102). Parallel computers configured to perform checkpointing for delayed alert creation according to embodiments of the present invention sometimes include thousands of compute nodes. In addition to Ethernet, JTAG, collective, and point to point, networks in such data processing systems may support many data communications protocols including for example TCP (Transmission Control Protocol), IP (Internet Protocol), and others as will occur to those of skill in the art. Various embodiments of the present invention may be implemented on a variety of hardware platforms in addition to those illustrated in FIG. 1.

Checkpointing for delayed alert creation in a distributed processing system in accordance with the present invention is generally implemented with computers, that is, with automated computing machinery. In the system of FIG. 1, for example, all the service nodes, I/O nodes, compute nodes, of the parallel computer are implemented to some extent at least as computers. For further explanation, therefore, FIG. 2 sets forth a block diagram of automated computing machinery comprising an exemplary computer (252) useful in performing checkpointing for delayed alert creation according to embodiments of the present invention. The computer (252) of FIG. 2 includes at least one computer processor (256) or ‘CPU’ as well as random access memory (268) (‘RAM’) which is connected through a high speed memory bus (266) and bus adapter (258) to processor (256) and to other components of the computer (252) and through an expansion bus to adapters for communications with other components of a distributed processing system (101).

Stored in RAM (268) is an event and alert analysis module (124), a module of automated computing machinery for performing checkpointing for delayed alert creation according to embodiments of the present invention. The event and alert analysis module (124) includes two incident analyzers, a monitor (204), and a checkpoint manager (299) according to embodiments of the present invention.

The checkpoint manager (299) performs checkpointing for delayed alert creation according to embodiments of the present invention by processing checkpoints from the incident analyzers. The monitor (204) is configured to perform checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. In the example of FIG. 2, the monitor (204) receives events from components of the distributed processing system and puts the received events in an event queue. The monitor (204) of FIG. 2 may receive events from components of the distributed processing system on their motion, may periodically poll one or more of the components of the distributed processing system, or receive events from components in other ways as will occur to those of skill in the art.

The incident analyzers include an event analyzer (208) and an alert analyzer (218). The event analyzer of FIG. 2 is a module of automated computing machinery capable of identifying alerts in dependence upon received events. That is, event analyzers typically receive events and produce alerts. In many embodiments, event analyzers are implemented in parallel. Often such event analyzers are assigned to a particular pool of events and may be focused on events from a particular component or caused by a particular occurrence to produce a more concise set of alerts.

The alert analyzer (218) of FIG. 2 is a module of automated computing machinery capable of identifying alerts for transmission from events and other alerts, identifying additional alerts for transmission, and suppressing unnecessary, irrelevant, or otherwise unwanted alerts identified by the event analyzer. That is, alert analyzers typically receive alerts and events and produce or forward alerts in dependence upon those alerts and events. In many embodiments, alert analyzers are implemented in parallel. Often such alert analyzers are assigned to a particular pool of alerts and may be focused on alerts with particular attributes to produce a more concise set of alerts.

In addition to the general functions described above, the event and alert analysis module (124) may be configured to perform checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. Specifically, the event and alert analysis module (124) is implemented as automated computing machinery configured to apply a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered. Following a crash and the loss of the corresponding alerts not recorded in an alert database, the event and alert analysis module is configured to generate new alerts based on the events in the events pool having the checkpoint. In response to completing processing of a new alert, the event and alert analysis module (124) determines whether the alert database has an entry corresponding to the processed new alert. If the alert database has an entry corresponding to the processed new alert, the event and alert analysis module (124) delivers the processed new alert without reporting the processed new alert to the alert database. If the alert database does not have an entry corresponding to the processed new alert, the event and alert analysis module (124) writes the processed new alert to a delivery queue and reports the processed new alert to an alert database including creating an entry within the alert database.

Also stored in RAM (268) is an operating system (254). Operating systems useful for relevant alert delivery according to embodiments of the present invention include UNIX™, Linux™, Microsoft XP™, AIX™, IBM's i5/OS™, and others as will occur to those of skill in the art. The operating system (254), event and alert analysis module (124), the event analyzer (208), the alert analyzer (218) in the example of FIG. 2 are shown in RAM (268), but many components of such software typically are stored in non-volatile memory also, such as, for example, on a disk drive (270).

The computer (252) of FIG. 2 includes disk drive adapter (272) coupled through expansion bus (260) and bus adapter (258) to processor (256) and other components of the computer (252). The disk drive adapter (272) connects non-volatile data storage to the computer (252) in the form of disk drive (270). Disk drive adapters useful in computers for checkpointing for delayed alert creation according to embodiments of the present invention include Integrated Drive Electronics (‘IDE’) adapters, Small Computer System Interface (‘SCSI’) adapters, and others as will occur to those of skill in the art. Non-volatile computer memory also may be implemented for as an optical disk drive, electrically erasable programmable read-only memory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, as will occur to those of skill in the art.

The example computer (252) of FIG. 2 includes one or more input/output (‘I/O’) adapters (278). I/O adapters implement user-oriented input/output through, for example, software drivers and computer hardware for controlling output to display devices such as computer display screens, as well as user input from user input devices (281) such as keyboards and mice. The example computer (252) of FIG. 2 includes a video adapter (209), which is an example of an I/O adapter specially designed for graphic output to a display device (280) such as a display screen or computer monitor. The video adapter (209) is connected to processor (256) through a high speed video bus (264), bus adapter (258), and the front side bus (262), which is also a high speed bus.

The exemplary computer (252) of FIG. 2 includes a communications adapter (267) for data communications with other computers (282) and for data communications with a data communications network (200). Such data communications may be carried out serially through RS-232 connections, through external buses such as a Universal Serial Bus (USW), through data communications data communications networks such as IP data communications networks, and in other ways as will occur to those of skill in the art. Communications adapters implement the hardware level of data communications through which one computer sends data communications to another computer, directly or through a data communications network. Examples of communications adapters useful for checkpointing for delayed alert creation according to embodiments of the present invention include modems for wired dial-up communications, Ethernet (IEEE 802.3) adapters for wired data communications network communications, and 802.11 adapters for wireless data communications network communications.

For further explanation, FIG. 3 sets forth a block diagram of an exemplary system for checkpointing for delayed alert creation and relevant alert delivery in a distributed processing system (102) according to embodiments of the present invention. The system of FIG. 3 includes an event and alert analysis module (124). The event and alert analysis module (124) of FIG. 3 receives in an event queue (306) a plurality of events (302) from one or more components of a distributed processing system (102). A component of a distributed processing system according to embodiments of the present invention may be a device of the distributed processing system or a process running on a device of the distributed processing. Such components are often capable of some form of event transmission, often for error or status reporting.

An event according to embodiments of the present invention is a notification of a particular occurrence in or on a component of the distributed processing system. Such events are sent from the component upon which the occurrence occurred or another reporting component to an event and alert analysis module according to the present invention. Often events are notifications of errors occurring in a component of the data processing system. Events are often implemented as messages either sent through a data communications network or shared memory. Typical events for event and alert analysis according to embodiments of the present invention include attributes such as an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component, and other attributes. An occurred time is the time at which the event occurred on the component. A logged time is the time the event was included in the event queue (306) and is typically inserted into the event by a monitor. An event type is a generic type of event such as for example, power error, link failure error, errors related to not receiving messages or dropping packets and so on as will occur to those of skill in the art. An event ID is a unique identification of the event. A reporting component is an identification of the component that reported the event. A source component is an identification of the component upon which the event occurred. In many cases, but not all, the reporting component and source component are the same component of the distributed processing system.

The event and analysis module (124) of FIG. 3 also includes a checkpoint manager (299) that is configured to perform checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention.

In the example of FIG. 3, the monitor (204) receives events from components of the distributed processing system and puts the received events (302) in the event queue (306). The monitor (204) of FIG. 3 may receive events from components of the distributed processing system on their motion, may periodically poll one or more of the components of the distributed processing system, or receive events from components in other ways as will occur to those of skill in the art.

The system of FIG. 3 also includes an event analyzer (208). The event analyzer (208) of FIG. 3 is a module of automated computing machinery configured to identify alerts in dependence upon received events. That is, event analyzers typically receive events and produce alerts. In many embodiments, multiple event analyzers are implemented in parallel. Often event analyzers are assigned to a particular pool of events and may be focused on events from a particular component or caused by a particular occurrence to produce a more concise set of alerts.

As mentioned above, in some embodiments of the present invention, more than one event analyzer may operate in parallel. As such, each event analyzer may maintain one or more events pools for performing checkpointing for delayed alert creation according to embodiments of the present invention. Assigning by the event analyzer the events to an events pool may therefore include selecting only events from one or more particular components. In such embodiments, particular components may be selected for a particular events pool to provide events associated with a particular period of time from a particular set of one or more components.

Assigning by the event analyzer the events to an events pool may also be carried out by selecting only events of a particular event type. In such embodiments, particular events may be selected for a particular events pool to provide events associated with a particular period of time from a particular set of event types. The event analyzer (208) in the example of FIG. 3 identifies in dependence upon the event analysis rules (310) and the events assigned to the events pool, one or more alerts (314). Event analyses rules (310) are a collection of predetermined rules for meaningfully parsing received events to identify relevant alerts in dependence upon the events.

The event analysis rules (310) of FIG. 3 include event arrival rules (330), events pool operation rules (332), event suppression rules (334), and events pool closure rules (336). The event arrival rules (330) are configurable predetermined rules for identifying alerts in dependence upon events in real time as those events are assigned to the events pool. That is, the event arrival rules (330) identify alerts in dependence upon events before closing the events pool. Such rules are typically predetermined to identify particular alerts in dependence upon attributes of those events. Event arrival rules may for example dictate identifying a particular predetermined alert for transmission to a systems administrator in dependence upon a particular event type or component type for the event or other attribute of that event. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error based upon more than one event, and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

The events pool operation rules (332) are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules dictating the amount to extend the initial predetermined period of time based on an arrival rate of events assigned to an events pool, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

The event suppression rules (334) are configurable predetermined rules for suppressing one or more events in a closed pool of events used in identifying alerts. That is, often events in the closed events pool may be duplicate events, redundant events, or otherwise unnecessary or unhelpful events in identifying alerts. Such suppression rules are typically predetermined to delete, drop, or otherwise ignore those suppressed events. Event suppression rules may for example dictate that more than a threshold number of events of a particular event type or component type are to be suppressed. Such rules are also flexible and may be tailored to a particular distributed computing system and its functions.

The events pool closure rules (336) are configurable predetermined rules for identifying alerts in dependence upon unsuppressed events in the closed events pool and alerts identified by the event arrival rules. That is, events pool closure rules identify new alerts in dependence upon one or more or even all of the unsuppressed events in the closed events pool. The events pool closure rules also identify alerts in dependence upon the alerts identified by the event arrival rules (330) or a combination of the alerts identified by the event arrival rules (330) and one or more of the unsuppressed events in the closed events pool.

The event analyzer (208) in the example of FIG. 3 sends all the alerts (314) identified by the event analyzer (208) to an alert analyzer (218). The alert analyzer of FIG. 3 is a module of automated computing machinery capable of identifying alerts for transmission from events and other alerts, identifying additional alerts for transmission, and suppressing unnecessary, irrelevant, or otherwise unwanted or unhelpful alerts identified by the event analyzer. That is, alert analyzers typically receive alerts and events and produce or forward alerts in dependence upon those alerts and events. In many embodiments, alert analyzers are implemented in parallel. The alerts (316) in the example of FIG. 3 are sent from the event analyzer (208) to the alert analyzer (218) through an alerts queue (316).

The alert analyzer (218) of FIG. 3 assigns each of the identified alerts (314) to an alerts pool (324). An alerts pool is a collection of alerts organized by the time of one or more the events causing the alert to be identified, the time the alert is identified, or other time as will occur to those of skill in the art. That is, alerts pools are a collection of alerts organized by time. Such alerts pools often provide the ability to analyze groups alerts identified and included in the alerts pool according to some time. Often such alerts pools are useful in identifying fewer and more relevant alerts in dependence upon multiple related events and multiple related alerts.

The alert analyzer (218) of FIG. 3 determines in dependence upon alert analysis rules (322) and the alerts in the alerts pool whether to suppress any alerts. Suppressing an alert is typically carried out by dropping the alert, deleting the alert or otherwise ignoring or not transmitting the suppressed alert to a component of the distributed processing system.

The alert analysis rules (322) are a collection of rules for suppressing one or more alerts to provide a more relevant set of alerts for transmission to a component of the distributed processing system, such as for example, for display to a systems administrator and to identify additional alerts for transmission to one or more components of the distributed processing system. Alert analysis rules for example may dictate that duplicate alerts are to be suppressed, alerts of a particular type for transmission to a particular component are to be suppressed, alerts of a particular type be transmitted to a particular component are to be suppressed and so on as will occur to those of skill in the art. Such alerts may be more meaningful to a component of the distributed processing system for automated error recovery or for a systems administrator who may otherwise be less informed by a number of raw unanalyzed alerts.

The alert analyzer (218) of FIG. 3 also has access to the events queue (306). The alert analyzer (218) of FIG. 3 in dependence upon the alert analysis rules may, in some embodiments select events from the events queue and determine whether to suppress any alerts in dependence upon the selected events. That is, alert analysis rules may also take into account events and their attributes for suppressing alerts and for identifying additional alerts for transmission to one or more components. Such events may be related to the alerts in the alerts pool or independent from such alerts.

The alert analyzer (218) of FIG. 3 transmits the unsuppressed alerts to one or more components of the distributed processing system. The alert analyzer may transmit the unsuppressed alerts to one or more components of the distributed processing system by sending the alert as a message across a data communications network, through shared memory, or in other ways as will occur to those of skill in the art. In the example of FIG. 3, the unsuppressed alerts (320) are transmitted to the terminal (122) for display to the systems administrator (128).

The alert analyzer (218) of FIG. 3 is also configured to identify in dependence upon alert analysis rules (322), the alerts in the alerts pool (324), and selected events (306) one or more additional alerts and transmitting the one or more components of the distributed processing system. The additional alerts may include one or more alerts not identified by the event analyzer. Such additional alerts may provide additional information to a component of the distributed processing system of a systems administrator.

In the system of FIG. 3, events (302) are received and analyzed by event analyzers (208) with event analysis rules (310). Based on the event analysis rules (310), the event analyzers (208) generate the alerts (314). These alerts may be sent to a delivery queue (399) for immediate delivery to the system administrator (128) and the distributed processing system (102). These alerts may also be sent to alert analyzers (218) for further processing and generation of additional alerts (320), which may also be provided to the delivery queue (399).

The event and alert analysis module (124) also includes an alert database (397) for recording alerts that have generated by the event and alert analysis module (124). In response to an alert being placed in the delivery queue, the event and alert analysis module (124) creates in the alert database (397), an entry corresponding to the alert. That is, an alert is ‘recorded’ in the alert database when the alert is placed in the delivery queue.

The event and alert analysis module (124) is also configured to create checkpoints that indicate event and alert processing information corresponding to the event analyzers and the alert analyzers. In the example of FIG. 3, the event and alert analysis module (124) creates a checkpoint (388) that includes alert data for a first alert (389) and a second alert (387). The checkpoints are useful for resuming event and alert processing following a crash. Specifically, the event and alert analysis module (124) applies a checkpoint to each event pool having events with corresponding alerts that have been generated and not delivered. That is, each checkpoint indicates events having corresponding alerts that are within the event and alert analysis module (124) but have not left the delivery queue (399). Accordingly, the event and alert analysis module may have multiple active event analyzer checkpoints—one for each event pool that created an alert that has not been completely processed by the alert analyzers.

Following a crash and the loss of the corresponding alerts not recorded in the alert database, the event and alert analysis module (124) generates new alerts based on the events in the event pool having the checkpoint. In response to completing processing of a new alert generated based on the events in the event pool having the checkpoint, the event and alert analysis module (124) determines whether the alert database (397) has an entry corresponding to the processed new alert. Determining whether the alert database has an entry corresponding to the processed new alert may be carried out by examining the database for an alert type or location information that matches the alert type or the location information of the processed new alert. For example, each alert may have an alert type and location information and each entry may indicate the alert type and the location information for a recorded alert.

If the alert database has an entry corresponding to the processed new alert, the event and alert analysis module (124) delivers the processed new alert to a component of the distributed processing system without reporting the processed new alert to the alert database (397). If the alert database (397) does not have an entry corresponding to the processed new alert, the event and alert analysis module (124) writes the processed new alert to a delivery queue and creates within the alert database (397), an entry corresponding to the generated alert. That is, the generated alert is written into a delivery queue for delivery to a component of the distributed processing system and the generated alert is recorded in the alert database as an entry.

For example, following a crash, alerts that were not within the delivery queue (399) at the time of the crash, will be recreated and recorded in the alerts database (397). However, alerts that were within the delivery queue (399) and thus were recorded in the alert database (397) before the crash will not be re-recorded in the alerts database (397). That is, by checking the alerts database (397) before recording an alert, the event and alert analysis module (124) may avoid duplicate entries corresponding to the same alert. To recreate alerts, the checkpoint (388) includes alert data, such as a unique alert identification number, associated with each alert based on the events in the event pool having the checkpoint.

When the alert has been delivered and processing of the alert is therefore done, the event and alert analysis module (124) informs the checkpoint (388) of the delivery. When all of the alerts associated with events within the event pool associated with the checkpoint (388) have been delivered, the checkpoint (388) can destroy itself. That is, the checkpoint (388) destroys itself upon receiving notification that the last outstanding alert associated with an event within the event pool has been delivered.

As mentioned above, checkpointing for delayed alert creation according to embodiments of the present invention may include assigning events to an events pool and those pools are administered according to embodiments of the present invention. For further explanation, FIG. 4 sets forth a diagram illustrating assigning events to an events pool according to embodiments of the present invention. An events pool (312) is a collection of events organized by the time of either their occurrence, by the time they are logged in the event queue, included in the events pool, or other time as will occur to those of skill in the art. That is, events pools are a collection of events organized by time. Such events pools often provide the ability to analyze a group of time related events and to identify alerts in dependence upon them. Often such events pools are useful in identifying fewer and more relevant alerts in dependence upon multiple related events.

Events pools according to embodiments of the present invention are typically operated according to events pool operation rules which are themselves often included in event analysis rules. Such events pool operation rules are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules dictating the amount to extend the initial predetermined period of time based on an arrival rate of events assigned to an events pool, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

Events are often assigned to an events pool according to their logged time. That is, events are typically inserted into the events pool in the order that they are received in the event queue. In the example of FIG. 4, the timing of the events pool (312) is initiated when the first event ‘Event 0’ (400) is assigned to the events pool (312) at time t₀. The events pool of FIG. 4 is initiated for a predetermined initial period of time from t₁ to t_(f). That is, upon receiving the first event ‘Event 0’ (400) the events pool of FIG. 4 has a predetermined initial period of time beginning at t₁ and ending at t_(f). The predetermined initial period of time may be configured in dependence upon a number of factors as will occur to those of skill in the art such as, the number of components in the distributed processing system, the frequency of receiving events, the types of events typically received and so on as will occur to those of skill in the art.

In the example FIG. 4, the initial period of time is extended for each new event assigned to the events pool during the predetermined initial period from t₁ to t_(f) by a particular period of time assigned to the event. In the example of FIG. 4 upon assigning ‘Event 1’ (402) to the events pool (312) the predetermined initial period of time t₀-t_(f) is extended by ‘Extension 1’ (406) having a time of e1 thereby creating a new time for closing the events pool (312) at t_(f+e1) if no other events are assigned to the pool before t_(f+e1). Similarly, in the example of FIG. 4 upon assigning ‘Event 2’ (404) to the events pool having a time of e2, the now extended period of time from t₀-t_(f+e1) is extended again by extension 2 (406) thereby establishing a new time for closing the pool at time t_(f+e1+e2) if no other events are assigned to the pool before t_(f+e1+e2) or before some maximum time for the events pool has expired. In this manner, the events pool is extended with each received event until a collection of events that may be usefully used to identify alerts is assigned to the events pool. According to embodiments of the present invention, the predetermined initial period of time may be extended based on an arrival rate at which events are assigned to an events pool.

In typical embodiments of the present invention, events pools may have a maximum duration that can no longer be extended. In such cases, a requirement may exist that an event that has not resided in the events pool for a threshold period of time be moved to a next events pool. In some embodiments, the attributes of such an event that is moved to the next events pool are used for relevant alert delivery with the initial events pool and in other embodiments; the attributes of such an event are used for relevant alert delivery with the next events pool to which that event is moved.

In the example of FIG. 4, when conditions are met to close the pool an events analyzer determines for each event (400, 402, 404) in the events pool (312) whether the event has been in the pool for its predetermined minimum time for inclusion in a pool. If the event has been in the pool for its predetermined minimum time, the event is included in the closed pool for event analysis for relevant alert delivery. If the event has not been in the pool for its predetermined minimum time, the event is evicted from the closed pool and included a next pool for event analysis for relevant alert delivery.

In many embodiments, a plurality of events pools may be used in parallel and one or more of such events pools are assigned to a particular events analyzer. In such embodiments, events analyzers may be directed to events in events pools having particular attributes.

As mentioned above, checkpointing for delayed alert creation according to embodiments of the present invention may include assigning alerts to an alerts pool and those pools are administered according to embodiments of the present invention. For further explanation, FIG. 5 sets forth a diagram illustrating assigning alerts to an alerts pool according to embodiments of the present invention. The alerts pool (324) of FIG. 5 operates in a manner similar to the events pool of FIG. 4. That is, the alerts pool according to the example of FIG. 5 includes alerts and the timing of the alerts pool begins with the first alert ‘Alert 0’ (500) at time t₀ and is configured to have a predetermined initial period of time t₀-tf. In the example of FIG. 5, the initial period of time is extended for each new alert assigned to the alerts pool in the predetermined initial period from t₁ to t_(f) by a particular period of time assigned to the alert. In the example of FIG. 5, upon assigning ‘Alert 1’ (502) to the alerts pool (324) the predetermined initial period of time t₀-t_(f) is extended by ‘Extension 1’ (506) having a time of e1 thereby creating a new time for closing the alerts pool (324) at t_(f+e1) if no other alerts are assigned to the pool before t_(f+e1). Similarly, in the example of FIG. 5 upon assigning ‘Alert 2’ (504) to the alerts pool having a time of e2, the now extended period of time from t₀-t_(f+e1) is extended again by ‘Extension 2’ (506) thereby establishing a new time for closing the pool at time t_(f+e1+e2) if no other alerts are assigned to the pool before t_(f+e1+e2) or before some maximum time for the alerts pool has expired. According to embodiments of the present invention, the predetermined initial period of time may be extended based on an arrival rate at which alerts are assigned to an alerts pool.

In typical embodiments of the present invention, alerts pools may have a maximum duration that can no longer be extended. In such cases, a requirement may exist that an alert that has not resided in the alerts pool for a threshold period of time be moved to a next alerts pool. In some embodiments, the attributes of such an alert that is moved to the next alerts pool are used for relevant alert delivery according to embodiments of the present invention with the initial alerts pool and in other embodiments, the attributes of such an alert are used for relevant alert delivery with the next alerts pool to which that alert is moved.

In the example of FIG. 5, when conditions are met to close the pool an alerts analyzer determines for each alert (500, 502, 504) in the pool (324) whether the alert has been in the pool for its predetermined minimum time for inclusion in a pool. If the alert has been in the pool for its predetermined minimum time, the alert is included in the closed pool for alert analysis for relevant alert delivery according to embodiments of the present invention. If the alert has not been in the pool for its predetermined minimum time, the alert is evicted from the closed pool and included a next pool for alert analysis for relevant alert delivery according to embodiments of the present invention.

In many embodiments, a plurality of alerts pools may be used in parallel and one or more of such alerts pools are assigned to a particular alerts analyzer. In such embodiments, alerts analyzers may be directed to alerts in alerts pools having particular attributes.

As mentioned above, checkpointing for delayed alert creation according to embodiments of the present invention may include the administration of one or more pools of incidents such as events, alerts or other incidents as will occur to those of skill in the art. For further explanation, FIG. 6 sets forth a flow chart illustrating an example method of performing checkpointing for delayed alert creation for incident analysis in a distributed processing system in a distributed processing system according to embodiments of the present invention. The method of FIG. 6 includes receiving (602) in an event queue a plurality of events (302) from one or more components of a distributed processing system. Attributes of events useful in performing checkpointing for delayed alert creation for incident analysis in a distributed processing system according to embodiments of the present invention may include an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component.

Receiving (602) in an event queue a plurality of events (302) from one or more components of a distributed processing system may be carried out by receiving an event initiated by one or more components of the data processing system and storing the event in the event queue according to the time in which the event occurred or according to the time the event was received. Receiving (602) in an event queue a plurality of events (302) from one or more components of a distributed processing system also may be carried out by polling a component for status and receiving in response an event and storing the event in the event queue according to the time in which the event occurred or according to the time the event was received.

The method of FIG. 6 also includes assigning (604) by an event analyzer each received event to an events pool (312). In some embodiments of the present invention, assigning (604) by an event analyzer each received event (302) to an events pool (312) may be carried out by assigning events to the events pool according to the logged time. Assigning (604) by an event analyzer each received event (302) to an events pool (312) may also be carried out in dependence upon attributes of the event. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event, the reporting component of the event, the event ID, the event type, and so on as will occur to those of skill in the art.

An events pool according to the method of FIG. 6 includes events occurring during a predetermined initial period of time and in the example of FIG. 6 assigning (604) by the event analyzer each received event to an events pool includes extending (626) for each event assigned to the events pool the predetermined initial period of time by a particular period of time assigned to the event.

The event analyzer includes event analysis rules (310) including, event arrival rules, events pool operation rules, event suppression rules, and events pool closure rules. Event arrival rules are configurable predetermined rules for identifying alerts in dependence upon events in real time as those events are assigned to the events pool. That is, event arrival rules identify alerts in dependence upon events before closing the events pool. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error based upon more than one event, and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

Events pool operation rules are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

Event suppression rules are configurable predetermined rules for suppressing one or more events in a closed pool of events used in identifying alerts. That is, often events in the closed events pool may be duplicate events, redundant events, or otherwise unnecessary or unhelpful events in identifying alerts. Such suppression rules are typically predetermined to delete, drop, or otherwise ignore those suppressed events. Event suppression rules may for example dictate that more than a threshold number of events of a particular event type or component type are to be suppressed. Such rules are also flexible and may be tailored to a particular distributed computing system and its functions.

Events pool closure rules are configurable predetermined rules for identifying alerts in dependence upon unsuppressed events in the closed events pool and alerts identified by the event arrival rules. That is, events pool closure rules identify new alerts in dependence upon one or more or even all of the unsuppressed events in the closed events pool. The events pool closure rules also identify alerts in dependence upon the alerts identified by the event arrival rules or a combination of the alerts identified by the event arrival rules and one or more of the unsuppressed events in the closed events pool.

The method of FIG. 6 also includes identifying (610) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (314). Identifying (610) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (314) may be carried out by identifying alerts in dependence upon one or more attributes of the events as that event is assigned to the events pool. Identifying (610) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (314) may be carried by comparing the attributes of the events to the event arrival rules and identifying as a result of the comparison one or more alerts. Such attributes may include the type of component from which the event was received, the type of component creating the event, the identification of the component creating the event, the time the event was created or received, an error reported in the event, and many others as will occur to those of skill in the art.

The method of FIG. 6 also includes closing (612), by the event analyzer in dependence upon the events pool operation rules, the events pool (312). Closing (612), by the event analyzer in dependence upon the events pool operation rules, the events pool (312) may be carried out by determining that conditions dictated by the events pool operation rules have been met to stop assigning new events to the events pool and identifying in dependence upon those events pool operation rules the particular events that are included in the closed pool of events.

Closing the events pool may be carried out by determining that the initial period of time for the events pool and any particular periods of time for events received in the events pool extended to the initial period of time have expired. In such cases, if no new events are received prior to the expiration of the initial period of time for the events pool and any particular periods of time for events received in the events pool extended to the initial period of time the pool is closed.

Closing the events pool may also be carried out by determining that a maximum duration for the events pool has expired. In such cases, regardless of the number of new events being received after a maximum duration for the events pool has expired the pool is closed. In such embodiments, a maximum duration for the events pool prevents the events pool from including more events than are useful for relevant alert delivery according to embodiments of the present invention.

The method of FIG. 6 also includes determining (614), by the events analyzer in dependence upon the event suppression rules, whether to suppress one or more events in the closed events pool (312). Determining (614), by the events analyzer in dependence upon the event suppression rules, whether to suppress one or more events in the closed events pool (312) may be carried out by determining in dependence upon the attributes of one or more events in the closed pool whether to delete, drop, or otherwise ignore one or more of the events in the closed pool.

The method of FIG. 6 includes identifying (616) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (617). Identifying (616) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (617) may be carried out by identifying alerts in dependence upon one or more attributes of the events as that event is assigned to the events pool. Identifying (616) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (617) may be carried out by selecting the unsuppressed events for the events pool, comparing the attributes of the unsuppressed events of the events pool to the pool closure rules, and identifying as a result of the comparison one or more additional alerts. Such attributes may include the type of component from which one or more of the unsuppressed events are received, the type of components creating the unsuppressed events, the identification of the component creating the unsuppressed events, the time the events were created or received, one or more errors reported by the events event, the number of events in the pool, and many others as will occur to those of skill in the art.

The method of FIG. 6 includes sending (618) by the event analyzer to an alert analyzer all the alerts identified by the event analyzer. Sending (618) by the event analyzer to an alert analyzer all the alerts (314) identified by the event analyzer may be carried out by sending a message containing the alerts from the event analyzer to the alert analyzer. Such a message may be sent from the event analyzer to the alert analyzer across a network, through shared memory, or in other ways as will occur to those of skill in the art.

The method of FIG. 6 includes assigning (620) by the alert analyzer the identified alerts to an alerts pool (324). An alerts pool according to the method of FIG. 6 has a predetermined initial period of time and in the example of FIG. 6 assigning (620) by the alert analyzer the identified alerts to an alerts pool (324) includes extending for each alert assigned to the alerts pool the predetermined initial period of time by a particular period of time assigned to the alert. Assigning (620) by the alert analyzer the identified alerts to an alerts pool (324) also may be carried out in dependence upon attributes of the alerts. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event that was used to identify the alert, the alert ID, the alert type, and so on as will occur to those of skill in the art.

The method of FIG. 6 includes determining (622) by the alert analyzer in dependence upon alert analysis rules (322) and the alerts in the alerts pool whether to suppress any alerts. Determining (622) by the alert analyzer in dependence upon alert analysis rules (322) and the alerts in the alerts pool whether to suppress any alerts may be carried out in dependence upon one or more attributes of the alerts. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event that was used to identify the alert, the alert ID, the alert type, and so on as will occur to those of skill in the art. In such embodiments, determining (622) by the alert analyzer in dependence upon alert analysis rules (322) and the alerts in the alerts pool whether to suppress any alerts may be carried out by comparing the attributes of the alerts in the alerts pool to the alert analysis rules and identifying as a result of the comparison one or more alerts for suppression according to the event analysis rules.

The method of FIG. 6 includes delivering (628) the unsuppressed alerts to one or more components of the distributed processing system. Delivering (628) the unsuppressed alerts to one or more components of the distributed processing system may be carried out by sending a message containing the alert to one or more components of the distributed processing system. In many cases, an alert may be sent as a message to a systems administrator advising the systems administrator of one or more occurrences within the distributed processing system.

As mentioned above, alert analysis rules may select additional alerts or suppress alerts in dependence upon events. In such embodiments, determining whether to suppress any alerts includes selecting events and determining whether to suppress any alerts in dependence upon the selected events. The method of FIG. 6 therefore also includes identifying (626) by the alert analyzer in dependence upon alert analysis rules (322), the alerts in the alerts pool (324), and any selected events one or more additional alerts and in the method of FIG. 6, delivering (628) the unsuppressed alerts also includes delivering (630) any additional alerts to one or more components of the distributed processing system.

For further explanation, FIG. 7 sets forth a flow chart illustrating an exemplary method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. The method of FIG. 7 includes an event and alert analysis module (124) applying (702) a checkpoint (788) to an events pool (312) having events (713) with corresponding alerts (715) that have been generated and not delivered. A checkpoint includes alert data that identifies alerts that have been generated but not delivered. An example of alert data is an alert identification number, such as a unique id (uuid). In the example of FIG. 7, the checkpoint (788) includes alert data associated with a first alert (787) and a second alert (789). Although only one checkpoint is illustrated in FIG. 7, the event and alert analysis module (124) may create multiple active event analyzer checkpoints—one for each events pool that created an alert that has not been delivered. The alert database (397) is a database for recording alerts that have been generated by the event and alert analysis module (124). For example, in response to an alert being placed in a delivery queue, the event and alert analysis module may create within the alert database, an entry corresponding to the alert. That is, an alert may be ‘recorded’ in the alert database when the alert is placed in a delivery queue (399). Applying (702) a checkpoint (788) to an events pool (312) having events (713) with corresponding alerts (715) that have been generated and not delivered may be carried out by identifying an alert associated with an event within an events pool; creating a checkpoint that includes alert data corresponding to the identified alert; identifying other alerts associated with one or more events of the events pool; and adding to the checkpoint, alert data corresponding to the identified other alerts.

The method of FIG. 7 also includes following a crash and the loss of the corresponding alerts (715) not recorded in the alert database, the event and alert analysis module (124) generating (704) new alerts (717) based on the events (713) in the events pool (312) having the checkpoint (788). Generating (704) new alerts (717) based on the events (713) in the events pool (312) having the checkpoint (788) may be carried out by examining the alert data to identify the alerts that were generated before the crash but were not delivered; and using the alert data to regenerate the identified alerts as new alerts.

The event and alert analyzer (124) is configured to process the new alerts (717). For example, alert analyzers within the event and alert analyzer may receive and process the new alerts, thus generating processed new alerts (718). In response to completing processing of a new alert, the event and alert analysis module (124) determines (706) whether the alert database (397) has an entry (796) corresponding to a processed new alert (718). Determining (706) whether the alert database (397) has an entry (796) corresponding to the processed new alert (718) may be carried out by examining the alert database (397) for information identifying the alert. For example, each alert may have an alert type and location information and entries within the alert database may record the alert type and location information of the alert associated with the entry.

If the alert database (397) has an entry corresponding to the processed new alert (718), the event and alert analysis module (124) blocks (708) the processed new alert from reporting to the alert database and blocks a user notification of the processed new alert. That is, the event and alert analysis module (124) ensures that duplicate entries in the database are not created for the same alert and that the user is notified in duplicate as well. If, however, the alert database (397) does not have an entry corresponding to the processed new alert (718), the event and alert analysis module (124) writes (710) the processed new alert (718) to the delivery queue (399) and reports (711) the processed new alert (718) to the alert database (397) including creating within the alert database (397), an entry (796) corresponding to the processed new alert (718). Creating within the alert database (397), an entry (796) corresponding to the processed new alert (718) may be carried out by writing and recording information associated with the alert into an entry of the alert database (397). The delivery queue (399) is configured to deliver the processed new alerts to one or more components of the distributed processing system.

By recording an alert when the alert is written to the delivery queue—not when it is created, the event and alert analysis module (124) removes the requirement for storing every created alert, which means that alerts may be given to alert analyzers more quickly. That is, delaying alert creation allows for additional alert analysis prior to recording the alert in the alert database, which could combine or eliminate unnecessary alerts, resulting in less database I/O and improved performance. Because alerts are not recorded until they are written to the delivery queue, some alerts that have not been delivered may be lost when there is a failure. To recover these in-memory alerts, the event and alert analysis module (124) maintains checkpoints that include information about alerts that are created so that as part of its recovery, the event and analysis module can create and re-inject the in-memory alerts for processing by the alert analyzers.

For further explanation, FIG. 8 sets forth a flow chart illustrating an additional method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. The method of FIG. 8 is similar to the method of FIG. 7 in that the method of FIG. 8 also includes applying (702) a checkpoint (788) to an events pool (312) having events (713) with corresponding alerts (715) that have been generated and not delivered; following a crash and loss of the corresponding alerts (715) not recorded in the alert database (397), generating (704) new alerts (717) based on the events (713) in the events pool (312) having the checkpoint (788); in response to completing processing of a new alert (718) generated based on the events (713) in the events pool (312) having the checkpoint (788), determining (706) whether the alert database (397) has an entry (796) corresponding to the processed new alert (718); if the alert database (397) has an entry corresponding to the processed new alert (718), blocking (708) the processed new alert (718) from reporting to the alert database (397) and from a user notification of the processed new alert; and if the alert database (397) does not have an entry corresponding to the processed new alert (718), writing (710) the processed new alert (718) to a delivery queue and reporting (711) the processed new alert (718) to the alert database (397) including creating within the alert database (397), an entry (796) corresponding to the processed new alert (718).

In the method of FIG. 8, each processed new alert (718) has a corresponding alert type (891) and location information (890). Examples of location information include an identifier of a component of the distributed processing system that generated an event corresponding to the alert.

In the method of FIG. 8, determining (706) whether an alert database (397) has an entry (796) corresponding to the processed new alert (718) includes determining (804) whether the alert database (397) has an entry with an alert type (881) and location information (880) matching the alert type (891) and the location information (890) of the processed new alert (718). Determining (804) whether the alert database (397) has an entry with an alert type (881) and location information (880) matching the alert type (891) and the location information (890) of the processed new alert (718) may be carried out by comparing the alert type and the location information of the entries within the alert database with the alert type and the location identification of the processed new alert.

For further explanation, FIG. 9 sets forth a flow chart illustrating an additional method of checkpointing for delayed alert creation in a distributed processing system according to embodiments of the present invention. The method of FIG. 9 is similar to the method of FIG. 7 in that the method of FIG. 9 also includes applying (702) a checkpoint (788) to an events pool (312) having events (713) with corresponding alerts (715) that have been generated and not delivered; following a crash and loss of the corresponding alerts (715) not recorded in an alert database (397), generating (704) new alerts (717) based on the events (713) in the events pool (312) having the checkpoint (788); in response to completing processing of a new alert (718) generated based on the events (713) in the events pool (312) having the checkpoint (788), determining (706) whether the alert database (397) has an entry (796) corresponding to the processed new alert (718); if the alert database (397) has an entry corresponding to the processed new alert (718), blocking (708) the processed new alert (718) from reporting to the alert database (397) and from a user notification of the processed new alert; and if the alert database (397) does not have an entry corresponding to the processed new alert (718), writing (710) the processed new alert (718) to a delivery queue (399) and reporting (711) the processed new alert (718) to the alert database (397) including creating within the alert database (397), an entry (796) corresponding to the processed new alert (718).

The method of FIG. 9 includes creating (901) a plurality (951) of checkpoints including a first checkpoint (950). In the example of FIG. 9, the first checkpoint (950) corresponds to a first events pool (960) having at least one event with a corresponding alert that has been generated and not delivered. Creating (901) a plurality (951) of checkpoints may be carried out by creating a checkpoint for each events pool that created an alert that has not been delivered; identifying an alert associated with an event within an events pool; creating a checkpoint that includes alert data corresponding to the identified alert; identifying other alerts associated with one or more events of the events pool; and adding to the checkpoint, alert data corresponding to the identified other alerts.

The method of FIG. 9 also includes the event and alert analysis module (124) determining (902) for the first checkpoint (950) that each alert (980) corresponding to the events (970) in the first events pool (960) has been delivered. Determining (902) for the first checkpoint (950) that each alert (980) corresponding to the events (970) in the first events pool (960) has been delivered may be carried out by determining that each alert has been recorded in the alert database; and determining that each alert has been transmitted from the delivery queue of the event and alert analysis module.

The method of FIG. 9 also includes the event and alert analysis module (124) destroying (904) the first checkpoint (950) in response to determining that each alert (980) corresponding to the events (970) in the first events pool (960) has been delivered. Destroying (904) the first checkpoint (950) may be carried out by inactivating the first checkpoint.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims. 

What is claimed is:
 1. A method of checkpointing for delayed alert creation, the method comprising: applying, by an event and alert analysis module, a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered; following a crash and the loss of the corresponding alerts not recorded in an alert database, generating, by the event and alert analysis module, new alerts based on the events in the events pool having the checkpoint; in response to completing processing of a new alert, determining, by the event and alert analysis module, whether the alert database has an entry corresponding to the processed new alert; if the alert database has an entry corresponding to the processed new alert, blocking, by the event and alert analysis module, the processed new alert from reporting to the alert database and blocking a user notification of the processed new alert; and if the alert database does not have an entry corresponding to the processed new alert, writing, by the event and alert analysis module, the processed new alert to a delivery queue and reporting the processed new alert to the alert database including creating within the alert database, an entry corresponding to the processed new alert.
 2. The method of claim 1 wherein the processed new alert has an alert type and location information; and wherein determining whether an alert database has an entry corresponding to the processed new alert includes determining whether the alert database has an entry with an alert type and location information matching the alert type and the location information of the processed new alert.
 3. The method of claim 1 wherein the checkpoint includes alert data for each of the corresponding alerts that have been generated and not delivered.
 4. The method of claim 3 wherein each alert data includes an alert identification.
 5. The method of claim 1 further comprising creating, by the event and alert analysis module, a plurality of checkpoints including a first checkpoint, the first checkpoint corresponding to a first events pool having at least one event with a corresponding alert that has been generated and not delivered.
 6. The method of claim 5 further comprising: determining for the first checkpoint, by the event and alert analysis module, that each alert corresponding to the events in the first events pool has been delivered; and in response to determining that each alert corresponding to the events in the first events pool has been delivered, destroying, by the event and alert analysis module, the first checkpoint.
 7. An apparatus for checkpointing for delayed alert creation in a distributed processing system, the apparatus comprising a computer processor and a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that when executed by the computer processor cause the apparatus to carry out the steps of: applying, by an event and alert analysis module, a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered; following a crash and the loss of the corresponding alerts not recorded in an alert database, generating, by the event and alert analysis module, new alerts based on the events in the events pool having the checkpoint; in response to completing processing of a new alert, determining, by the event and alert analysis module, whether the alert database has an entry corresponding to the processed new alert; if the alert database has an entry corresponding to the processed new alert, blocking, by the event and alert analysis module, the processed new alert from reporting to the alert database and blocking a user notification of the processed new alert; and if the alert database does not have an entry corresponding to the processed new alert, writing, by the event and alert analysis module, the processed new alert to a delivery queue and reporting the processed new alert to the alert database including creating within the alert database, an entry corresponding to the processed new alert.
 8. The apparatus of claim 7 wherein the processed new alert has an alert type and location information; and wherein determining whether an alert database has an entry corresponding to the processed new alert includes determining whether the alert database has an entry with an alert type and location information matching the alert type and the location information of the processed new alert.
 9. The apparatus of claim 7 wherein the checkpoint includes alert data for each of the corresponding alerts that have been generated and not delivered.
 10. The apparatus of claim 9 wherein each alert data includes an alert identification.
 11. The apparatus of claim 7 further comprising computer memory having disposed within it computer program instructions that when executed by the computer processor cause the apparatus to carry out the steps of: creating, by the event and alert analysis module, a plurality of checkpoints including a first checkpoint, the first checkpoint corresponding to a first events pool having at least one event with a corresponding alert that has been generated and not delivered.
 12. The apparatus of claim 11 further comprising computer memory having disposed within it computer program instructions that when executed by the computer processor cause the apparatus to carry out the steps of: determining for the first checkpoint, by the event and alert analysis module, that each alert corresponding to the events in the first events pool has been delivered; and in response to determining that each alert corresponding to the events in the first events pool has been delivered, destroying, by the event and alert analysis module, the first checkpoint.
 13. A computer program product for checkpointing for delayed alert creation in a distributed processing system, the computer program product disposed upon a computer readable storage medium, the computer program product comprising computer program instructions that when executed by a computer cause the computer to carry out the steps of applying, by an event and alert analysis module, a checkpoint to an events pool having events with corresponding alerts that have been generated and not delivered; following a crash and the loss of the corresponding alerts not recorded in an alert database, generating, by the event and alert analysis module, new alerts based on the events in the events pool having the checkpoint; in response to completing processing of a new alert, determining, by the event and alert analysis module, whether the alert database has an entry corresponding to the processed new alert; if the alert database has an entry corresponding to the processed new alert, blocking, by the event and alert analysis module, the processed new alert from reporting to the alert database and blocking a user notification of the processed new alert; and if the alert database does not have an entry corresponding to the processed new alert, writing, by the event and alert analysis module, the processed new alert to a delivery queue and reporting the processed new alert to the alert database including creating within the alert database, an entry corresponding to the processed new alert.
 14. The computer program product of claim 13 wherein the processed new alert has an alert type and location information; and wherein determining whether an alert database has an entry corresponding to the processed new alert includes determining whether the alert database has an entry with an alert type and location information matching the alert type and the location information of the processed new alert.
 15. The computer program product of claim 13 wherein the checkpoint includes alert data for each of the corresponding alerts that have been generated and not delivered.
 16. The computer program product of claim 15 wherein each alert data includes at least one of an alert identification, an alert location, and an alert type.
 17. The computer program product of claim 13 further comprising computer program instructions that when executed by a computer cause the computer to carry out the steps of creating, by the event and alert analysis module, a plurality of checkpoints including a first checkpoint, the first checkpoint corresponding to a first events pool having at least one event with a corresponding alert that has been generated and not delivered.
 18. The computer program product of claim 17 further comprising computer program instructions that when executed by a computer cause the computer to carry out the steps of: determining for the first checkpoint, by the event and alert analysis module, that each alert corresponding to the events in the first events pool has been delivered; and in response to determining that each alert corresponding to the events in the first events pool has been delivered, destroying, by the event and alert analysis module, the first checkpoint.
 19. The computer program product of claim 13, wherein the computer readable medium includes a signal bearing medium.
 20. The computer program product of claim 13, wherein the computer readable medium includes a storage medium. 